Skip to content

Update jdx/mise-action action to v5.3.0 - #55

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/jdx-mise-action-5.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/jdx-mise-action-5.x

Conversation

@renovate

@renovate renovate Bot commented Nov 21, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
jdx/mise-action action minor v5.2.10 → v5.3.0

Release Notes

jdx/mise-action

v5.3.0: : New mise_env input exports MISE_ENV to later steps

Compare Source

A new mise_env input sets the mise environment for the action and exports MISE_ENV to every later step in the job. mise run and mise x in later steps now load the same mise.<env>.toml configs that the action installed and cached.

Added

  • mise_env input. Before this change, setting MISE_ENV in the action step's env: only applied inside the action. Later steps never saw it and quietly fell back to the base config. Job-level env: worked, but composite actions that pick the environment from their own inputs had to write MISE_ENV to GITHUB_ENV themselves, and security linters such as zizmor flag that. The new input handles the export for you:

    - uses: jdx/mise-action@v5
      with:
        mise_env: ci # loads mise.ci.toml on top of mise.toml
    - run: mise run test # also runs with MISE_ENV=ci

    In a composite action:

    runs:
      using: composite
      steps:
        - uses: jdx/mise-action@v5
          with:
            mise_env: ${{ inputs.haskell == 'true' && 'ci' || 'ci-no-haskell' }}

    The input accepts one or more environments, such as ci or ci,linux. The action exports it before computing the cache key, so {{mise_env}} in a custom cache_key, mise install, and later steps all use the same value. If MISE_ENV is already set, the input takes priority, the same way mise_dir takes priority over MISE_DATA_DIR. If you leave the input unset, nothing changes, and a step-level MISE_ENV still isn't exported. (#​745 by @​jdx with @​veimox and @​cprecioso, closes #​447)

Full Changelog: jdx/mise-action@v5.2.10...v5.3.0


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@github-actions

Copy link
Copy Markdown

dnscontrol preview

CONCURRENTLY checking for 3 zone(s)
Waiting for concurrent checking(s) to complete...DONE
CONCURRENTLY gathering records of 3 zone(s)
Waiting for concurrent gathering(s) to complete...DONE
******************** Domain: junit.org
******************** Domain: apiguardian.org
******************** Domain: opentest4j.org
Done. 0 corrections.

Build log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants